Important: The commands or keywords/variables that are available are dependent on platform type, product version, and installed license(s).aka-v1: Specifies that the AKA-v1 algorithm will be used for subscribers using this access profile.
custom-md5: Specifies that custom algorithm HTTP-Digest-MD5 will be used for subscribers using this access profile.
md5: Specifies that the MD5 algorithm will be used for subscribers using this access profile. This is the default setting for this command.
The following command sets the authentication type for subscribers using this access profile to md5:
timeout sip { 3gpp-d sec | 3gpp-t1 msec | 3gpp-t2 sec | 3gpp-t4 sec | c sec | d sec | invite-expiry sec | t1 msec | t2 sec | t4 sec }
sip { 3gpp-d sec | 3gpp-t1 msec | 3gpp-t2 sec | 3gpp-t4 sec | c sec | d sec | invite-expiry sec | t1 msec | t2 sec | t4 sec }
3gpp-d sec: This time is used to control the retransmission of 200OK messages to INVITEs after an ACK is sent. The ACK transaction is cleared after this period. This timer is applicable only for unreliable transport.
sec must be an integer from 0 to 2147483646.
3gpp-t1 msec: This timer is used to control the time interval between each retransmission. The interval doubles after each retransmission. This is used by P-CSCF/A-BG only when it sending message toward the UE. Example: T1, 2T1, 4T2, etc. This timer is applicable only for unreliable transport.
msec must be an integer from 0 to 2147483646.
3gpp-t2 sec: This timer is used to control the period for which the request continues to get retransmitted. This is used by P-CSCF/A-BG only when it sending message toward the UE. This timer is applicable both for reliable and unreliable transport.
sec must be an integer from 0 to 2147483646.
3gpp-t4 sec: This timer is used to control the period for which the final response to non-invite transaction should be buffered. The buffered response for the retransmitted non-invite request should be sent within that interval. This timer is applicable only for unreliable transport.
sec must be an integer from 0 to 2147483646.
c sec: This timer is used for an INVITE transaction; if the response is a provisional response with status codes 101 to 199 inclusive (anything but 100), the proxy must reset timer C for that client transaction. The timer may be reset to a different value, but this value must be greater than 3 minutes (180 seconds). When timer C in S-CSCF fires first, S-CSCF will send CANCEL request to Terminating P-CSCF and Terminating P-CSCF will send CANCEL request to UAS .
sec must be an integer from 180 to 2147483646.
d sec: This time is used to control the retransmission of 200 OK to INVITE after ACK is sent. The ACK transaction will be cleared after this interval. This timer is applicable only for unreliable transport.
sec must be an integer from 0 to 2147483646.
invite-expiry sec: This timer is used by SIP while acting as UA Role and no final response is received for the INVITE request sent. This timer is applicable for both reliable and unreliable transport.
sec must be an integer from 0 to 2147483646.
t1 msec: Specifies the time interval (in milliseconds) between each retransmission. The interval doubles after each retransmission, for example: T1, 2T1, 4T2, etc. This timer is applicable only for unreliable transport.
msec must be an integer from 0 to 2147483646.
t2 sec: This timer is used to control the period for which the request keeps getting retransmitted. This timer is applicable both for reliable and unreliable transport.
sec must be an integer from 0 to 2147483646. The recommended minimum value for this parameter is 4 seconds.
t4 sec: This timer is used to control the period for which the final response to non-invite transaction should be buffered so as to send the buffered response for the retransmitted non-invite request within that interval. This timer is applicable only for unreliable transport.
sec must be an integer from 0 to 2147483646.
The following command sets the SIP d timer to 64 seconds:
